- Main Page
- Information on the Institution
- General Description of the Institution
- Address of İzmir University of Economics
- Academic Authorities
- Academic Calendar
- Recognition of Prior Learning
- Recognition of Study Abroad
- List of Programs Offered
- General Admission Requirements
- General Registration Procedures
- ECTS Credit Allocation
- Grading
- Arrangements for Academic Guidance
- Internationalization
- Institutional ECTS Coordinator
- Departmental Erasmus Coordinators
- Degree Programs
- Software Engineering
- Qualification Awarded
- Level of Qualification
- Specific Admission Requirements
- Qualification Requirements and Regulations
- Recognition of Prior Learning
- Profile of the Program
- Program Outcomes
- Course & Program Outcomes Matrix
- Occupational Profiles of Graduates
- Access to Further Studies
- Program Structure
- Course Structure Diagram with Credits
- Exam Regulations & Assessment & Grading
- Graduation Requirements
- Mode of Study
- Program Director (or Equivalent)
- Evaluation Questionnaires
- Courses
- General Information For Students
- About İzmir
- Cost of Living
- Accommodation
- Meals
- Medical Facilities
- Facilities for Special Needs Students
- Career Guidance Center
- Insurance
- Financial Support for Students
- Registrar's Office
- Learning Facilities
- International Programs
- Practical Information for Exchange Students
- Language Courses
- Internships
- Sports and Leisure Facilities
- Student Associations
- Useful Phone Numbers
- Diploma Supplement
- Erasmus Policy Statement
- National Qualifications
- Bologna Commission
11111
COURSE INTRODUCTION AND APPLICATION INFORMATION
se.cs.ieu.edu.tr
| Course Name | |
| Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
|---|---|---|---|---|---|
| Fall |
| Prerequisites |
| ||||||||
| Course Language | |||||||||
| Course Type | Required | ||||||||
| Course Level | - | ||||||||
| Mode of Delivery | - | ||||||||
| Teaching Methods and Techniques of the Course | |||||||||
| Course Coordinator | |||||||||
| Course Lecturer(s) | |||||||||
| Assistant(s) | |||||||||
| Course Objectives | |
| Learning Outcomes | The students who succeeded in this course;
|
| Course Description |
|
| Core Courses | X |
| Major Area Courses | ||
| Supportive Courses | ||
| Media and Managment Skills Courses | ||
| Transferable Skill Courses |
WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES
| Week | Subjects | Required Materials |
| 1 | Introduction and case studies, challenges in information systems development | Bennett, Ch1, Ch2 |
| 2 | Meeting the challenges. What is object orientation? | Bennett, Ch3, Ch4 |
| 3 | Modeling concepts | Bennett, Ch 5.1 & Ch. 5.2 |
| 4 | Modeling concepts | Bennett, Ch 5.3 & Ch. 5.4 |
| 5 | Requirements capture | Bennett, Ch 6 |
| 6 | Requirements capture | Bennett, Ch 6 |
| 7 | Review & Midterm exam. Please make sure that you attend the exam on time, any excuses including medical ones will not be accepted, as the possibility of having a make-up exam seems to be remote under the circumtances. | |
| 8 | Requirement analysis | Bennett, Ch 7 |
| 9 | Refining the requirements model | Bennett, Ch 8 |
| 10 | Object interaction | Bennett, Ch 9 |
| 11 | Specifying operations | Bennett, Ch 10 |
| 12 | Moving into design | Bennett, Ch 12 |
| 13 | Systems design and architecture | Bennett, Ch 13 |
| 14 | Detailed design | Bennett, Ch 14 |
| 15 | Review of the Semester | |
| 16 | Review of the Semester |
| Course Notes/Textbooks | ObjectOriented Systems Analysis and Design: Using UML, 4/e, Simon BennettSteve McRobbRay Farmer, McGrawHill, 2010, ISBN: 0077125363 |
| Suggested Readings/Materials | Software Engineering 8, Ian Sommerville, 8th Ed. Addison Wesley, 2007,ISBN 0321313798Software Engineering, Roger S. Pressman, Darrel Ince, McGrawHillPublishing Co.; 5Rev Ed edition (2007), ISBN: 9780077096779Software Specification and Design: An Engineering Approach, by Ph.D., JohnC. Munson, AUERBACH; 1 edition (2005), ISBN: 9780849319921An Introduction to Requirements Engineering, Ian K Bray, AddisonWesley(2002), ISBN: 9780201767926 |
EVALUATION SYSTEM
| Semester Activities | Number | Weigthing |
| Participation | ||
| Laboratory / Application | ||
| Field Work | ||
| Quizzes / Studio Critiques | ||
| Portfolio | ||
| Homework / Assignments | ||
| Presentation / Jury | ||
| Project | 1 | 30 |
| Seminar / Workshop | ||
| Oral Exam | ||
| Midterm | 1 | 30 |
| Final Exam | 1 | 40 |
| Total |
| Weighting of Semester Activities on the Final Grade | 2 | 60 |
| Weighting of End-of-Semester Activities on the Final Grade | 1 | 40 |
| Total |
ECTS / WORKLOAD TABLE
| Semester Activities | Number | Duration (Hours) | Workload |
|---|---|---|---|
| Course Hours (Including exam week: 16 x total hours) | 16 | 2 | 32 |
| Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
| Study Hours Out of Class | 16 | 4 | |
| Field Work | |||
| Quizzes / Studio Critiques | |||
| Portfolio | |||
| Homework / Assignments | |||
| Presentation / Jury | |||
| Project | 1 | 70 | |
| Seminar / Workshop | |||
| Oral Exam | |||
| Midterms | 1 | 14 | |
| Final Exams | 1 | 18 | |
| Total | 198 |
COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP
| # | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
| 1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
| 2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
| 3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
| 4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
| 5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | X | ||||
| 6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | X | ||||
| 7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | X | ||||
| 8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | X | ||||
| 9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
| 10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
| 11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
| 12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
| 13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest